home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Languguage OS 2
/
Languguage OS II Version 10-94 (Knowledge Media)(1994).ISO
/
language
/
vista
/
readme
< prev
Wrap
Text File
|
1992-01-16
|
5KB
|
136 lines
To build Vista:
[ Vista is built using the GNU software
bison and flex (similar to the Unix
utilities yacc and lex). If theye are
not installed on your system, install
them from the directories Bison and
Flex first. They are used in building
libae.a (in ./src/lib/ae), and that
Makefile may need to be changed to
reflect the path name to these two
utilities. ]
Make sure that the MAKE variables described below are set
properly in at least the Makefile in this directory.
The values set in this directory should propagate down to
the subdirectories.
Then, type make. This should build the libraries and binary
files needed for Vista. The directories are contents after
the makefile should be something like this, though the file
sizes may vary due to system differences:
./bin:
total 1928
-rwxr-xr-x 1 username 114688 Sep 16 19:08 ae_dm
-rwxr-xr-x 1 username 1630208 Sep 16 19:08 vista
-rwxr-xr-x 1 username 106496 Sep 16 19:08 vm_dm
./lib:
total 896
-r--r--r-- 1 username 689488 Sep 16 19:04 libvista.a
The binary files are executed from this directory. If you
move them elsewhere, the variable V_BIN described below
must be changed before building Vista to reflect their eventual
destination.
The directory ./data is used as distributed. You may wish to
move the entire directory elsewhere. if so, be sure to change
V_DATA described below.
The X Resource Manager application defaults file for Vista is
in the data directory. This should be copied to
/usr/lib/X11/app-defaults/Vista
or some other appropriate place on your system.
To run Vista:
Two example programs have been provided: whams3d, a finite
element code and jac2, a one-sided Jacobi method (iterative
eigenvalue method). Change to the directory ./example and
then to either jac or wham. Type make to make the application.
If the application defaults file has NOT been installed yet,
then you must make this information available to the X
resource manager in one of two other ways:
1. Copy the application defaults file to ~/app-defaults/Vista
and set the environment variable XAPPLRESDIR to ~/app-defaults.
or
2. Set the environment variable XENVIRONMENT to the full path
name of the file whereever you have it. Probably in
the directory of the MAKE variable V_DATA described below.
For example, ${VISTA_TOP}/data/Vista.
Normally, Vista (the visualization manager) is run on the local
workstation. Just execute the program .../bin/vista (whatever
the full path name is). The application is run in a rlogin
window (remote login shell) on another system. After the Vista
display appears, start the application in this other window.
(To do this type whams3d.s or jac2, depending on the example).
After several seconds you should see the message:
"Received connection from <remote host>"
in the Vista status window. You are now ready to add variables
to Vista and display them as desired.
Unless variables have been added with Vista "insert" calls
(like CALL AV2I(...)), they will be named with the routine
name, two accents and the variable name. For example, in
jac2, the variable of interest is hybr01``vv to view the
2-dimensional array solution.
In whams3d, interesting variables to add are (case is significant):
NTSTEP - time step
XC, YC, ZC - the X, Y, and Z coordinate arrays
xdisp, ydisp, zdisp - the X, Y, and Z displacement arrays
NNODE - number of nodes
NELE - number of elements
kdvcon - element connectivity array
remember also to toggle the "row major"/"column major" state.
Make Variables:
Make sure that the following variables are set in the Makefile
in this directory. These are propageted to the sub-directories.
These are used in the installation and also may compile into the
Vista modules for default path names to some files.
Only the VISTA_TOP and possibly X/MOTIF variables must be changed.
The others will have reasonable defaults enabling you to build Vista.
VISTA_TOP = set to this directory; top level for Vista
THIS MUST BE SET TO AN ABSOLUTE PATHNAME
V_BIN = path to the installed binaries for the
modules of Vista
Default: ${VISTA_TOP}/bin
V_DATA = path to the data files Vista uses during
execution. E.g., public color maps, pixmaps, etc.
Default: ${VISTA_TOP}/data
The next variables should need no change, they are only used for installation
V_LIB = path to the libraries used to build Vista
Default: ${VISTA_TOP}/lib
V_INC = path to the include files used to build Vista
Default: ${VISTA_TOP}/include
V_CFLAGS = flags passed to cc. E.g. -g
Default: -D_NO_PROTO -D_VFORK -DVersionDate=
The -D_NO_PROTO is required since many C compilers do not handle
ANSI C Function prototypes. Vista is written without prototypes,
and the X11/Motif include files need to know this.
The -D_VFORK will use VFORK instead of FORK where possible
(e.g., Berkeley 4.2-derived systems). It's only purpose is
to save a bit of resources. If your system does not support
VFORK, then just remove this define.
The -DVersionDate compiles the date into each module for identifing
different versions.
These are the libraries to search for the X11, Release 4
and Motif libraries.
X_LIB = -lXt -lX11
MOTIF_LIB= -lXm